Common J2EE/Java EE Fallacies

At the beginning of almost every project, there is an intense (almost religious) discussion about using or not using J2EE. Almost every time I'm faced with the following fallacies:

1. J2EE/JEE is only EJB technology.
2. EJBs are too complex.
3. We have only to consider ther development phase. The maintenance and production is not important.
4. Lean POJOs and transparent persistency is easier to understand for a beginner, than heavyweight EJBs.
5. JMS, JCA, JTA, JNDI, XA are too complex, too heavy and aren't needed at all. A lean inversion of control container could replace all this technologies.
6. CMP 2.0/CMP 3.0  persistence is too complex, it is much easier to implement the persistence with a simple dataset framework or just using JDBC.
7. Monitoring, management, profiling are not necessary.
8. It is very easy to implement everything you want in a web container.
9. It is sufficient to ensure the functionality of a distributed application with unit- and integration-tests.
   
10. and JEE will die. :-)