anonymous wrote : But it still puzzles me as to how or why this exact same set up worked and still works on jboss 3.2.3!! Here's the answer :) anonymous wrote : Since the upgrade to 3.2.7 / 4.0.2, this doesn't work anymore. This is a side effect of the resolution to http://jira.jboss.com/jira/browse/JBAS-275#action_12315001 : To avoid clashes between two identically-named EJBs, a generated hash-code is now appended to the JNDI name to make them unique *unless a local-jndi-name value is provided in the deployment descriptor* View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049464#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...