Bind your local home in the java:/ namespace if you don't want it to be available
from a remote lookup.
You'll find the local home is completely unusable from a remote VM.
Thanks for the reply. I know the local is not usable from a remote JVM - hence my surprise that the lookup returned a non-null object for a local. We have code that tries first to find the local home and use that if successful. If an exception is thrown - the lookup fails, then we look for the remote home. This way we don't have to worry if our ServiceLocator is being used inside the container or out.
We'll give your suggestion a try and see if that yields better results.