Hi Kyle,
EJBReference idea is great. We are having around 1000 entity beans we would have to develop a tool to generate the code and will manage to put EJBReference in deployment descriptor.
About your question on how PowerTier manages LDAP is:
In PowerTier5.12 there is a deployment file(.ptc) in which one has a support to configure different naming service, so here we give all the naming service properties(like factory,provider url etc). I have to say that this deployment file is not according to EJB specs.
Now when you publish the beans you can give a name of the server running. While publishing PowerTier takes help of ptc also.
Now in LDAP PowerTier has a Finder Object for each running application server. This Finder Object is PowerTier specific and not according to EJB specs.
The name of the finder Object is as follows:
Suppose we give a name to server as Release1 then PowerTier will have a finder object with the name Finder,PowerTierRelease1. So client first looks up on Finder in LDAP and than on Finder object we call a method getHome which will return the actual EJBHome.
So total archictecture is not 100% EJB compliant but thats the this works.