Think you can register your remote beans on only one jndi,
that would do the trick i think.
Wessel de Roode
....when accessing EJBs remotely from a separate JVM. I don't really know for sure but I've always worked from the assumption that one server's JNDI directory only listed things from the same JVM, but I don't really know a lot about JNDI.
Every time I've had the client and the EJB server running in separate JVMs, I've always written JNDI lookup code in the client. I can't imagine how it would work any other way nor can I imagine how you could declare everything you need within the deployment descriptors.
The client JNDI lookup is not too hard to do, so I just do it that way.