The rationale for using env-entries instead of hardcoding the JNDI names into your
Java code is... Oops. I slipped it out already
If your code refers to resources (including other EJBs) by a logical name, you don't have to worry about your chosen JNDI name being unavailable for some reason when you try to deploy your application.