You don't want an EJB to appear in the HA-JNDI namespace. If it does, something is broken. Each server binds a proxy for the EJB in JNDI. The HA-JNDI tree is a replicated namespace; that means if each server bound their proxy in it, at any time only one proxy would be bound -- the one from the last server to do the binding. That can lead to problems. If the EJBs are deployed homogenously across the cluster, the cost of having the HA-JNDI service check the HA-JNDI tree, find nothing, and then check the local JNDI tree on the machine handling the lookup is very low. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968704#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...