Today I run into a problem with my EJB 3.1 application after I tried to deploy more than one app with the same EJB module on the same glassfish domain. This results in a JNDI-Naming conflict telling you, that the EJB name is already bound. But since the new concept of JEE6 global portable jndi names this should not happen?
Here is a discussion about the problem: http://home.java.net/node/702307
The solution is quite simple as Glassfish provides a new property to disable the generation of the glassfish-specific non-portable jndi names (which were only provided because of backward compatibility. Simply add the param 'disable-nonportable-jndi-names' with the value 'true' directly into the EJB-Container additional-property section. This will avoid the create of thus names.
See also the following pages for more deails about this topic: