Just to be clear, you solved the issue right? Want to make sure that this is not a genuine bug in EJB3.1 implementation.
Reply to this message by going to Community
Start a new discussion in JNDI and Naming at Community