Worse, the first two of the above things happened to me while demonstrating things in Egypt. Firstly, my flatmate Lou Ruppert was in the first scenario—he has a very slow laptop, which is okay when he's doing his daily web development, via Tomcat. He hasn't used EJBs and web services and has no need to do so, so we disabled the J2EE module. But he wanted to upgrade an old web.xml file from 2.3 to 2.4. I said: "Look in the helpfiles, because I wrote a help topic which describes exactly how you do that." When he looked in the helpfiles, he found nothing. Only after I remembered that it was part of the J2EE module did I realize the cause of our being unable to find the help topic. Secondly, while demonstrating new 5.0 functionality to the AUC students in Cairo, I wanted to show them how a J2SE application can consume web services in 5.0. Again, the J2EE module had been disabled, and only after realizing that was it possible to continue with the demonstration. (If they had disabled a module called "web services", they would probably have been more aware of what functionality they had excluded, rather than something as amorphous as "J2EE".)
The third point above is something that NetBeans Evangelist Gregg Sporar pointed out to me—JSPs and servlets belong to J2EE. Whatever the case, though, I think it would be helpful to split the J2EE module into (at least) three—"EJB", "web services", and "application servers". I'm guessing there's some technical reason for why this hasn't been done already, but I'm hoping that this is possible somehow. Because, the current status is not very satisfactory—the term "J2EE" is just not transparent enough.