Is javax.naming.InitialContext ThreadSafe?

[Debopam Poddar]

Currently I am use following code to lookup EJB3 sateless session beans for normal POJO class. (We are in JEE5 so we can not inject Stateless Session Beans in normal POJO class I have to use look up)

import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;

import org.apache.log4j.Logger;

public Object getEJB(String jndiName) {

				logger.debug("WEBSPHERE EJB Lookup : " + jndiName);
				String modifiedJndiName = "";
				Hashtable<Object, Object> properties = new Hashtable<Object, Object>();
				properties.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
				properties.put(Context.PROVIDER_URL, "iiop://localhost:2809");
				try {
					Context context = new InitialContext(properties);
					logger.debug("WEBSPHERE EJB Lookup Modified JNDI Name: " + modifiedJndiName);
					return context.lookup("ejblocal:"+modifiedJndiName);
				}catch (NamingException ne) {
					logger.debug("Naming Exception occurred :"+jndiName +">>>"+ne.getMessage());
					logger.error(ne.getMessage(), ne);
				}

				return null;
			}

So is Context object is ThredSafe? should I create Context object for each call [as shown in this code snippet] or I can reuse the Context for all threads?