After using EJB's for a while I think the your company policy may well be right. The whole EJB container and the unnecessary complexity it entails needs to be completely rethought, particularly in the areas of CMT, CMP, CMR & deployment. I'm hopeful that EJB 3.0 through its use of the best parts of the Hibernate etc spec will go a long way to making this happen.
It
is possible to build elegant, easy to maintain systems using EJBs however my experience is that not many people know how to (despite what they say). It's simply far too easy to get it wrong and end up with a monster.
For the majority of my systems I prefer to use Apache,
Tomcat, JSP/Servlets and Hibernate/DAO - the systems work well, don't lack functionality and are much less complicated to build, deploy & maintain.
Your mileage may vary.
Treval