I'm pretty sure I mentioned that it was a servlet container ....
Yep, I most certainly did.
JEE is a rebrand of enterprise java, nothing more. It came in with the switch from Java 1.4 to Java 5 (internally still called 1.5). JEE 5/6 is much nicer, but not that much nicer. Especially when (in my experience) most development is done using the many non spec frameworks around (spring/ hibernate being chief) for final deployment on Tomcat. And honestly, EJB? It was the wrong solution. originally, and only got a bit better by becoming a standardised version of hibernate, which is _still_ better.
Servlets are part of the enterprise java spec (whatever you decide to call it), so its right to say they are part of enterprise java. Jetty has been around in one form or another since 2000, similar with Tomcat, which was the original reference implementation for servlets.
I was discussing that its amusing that they rail against the Java 'containers' and then use one of them in their example. They explicitly mention Tomcat as something they want to move away from, however they fire up an equivalent. I could write code that starts up Tomcat in almost the exact same way as the Jetty example they provide, and in a similar amount of code.
As a side note, the 'annotation based facilities' are to a large extent available outside of the enterprise containers, although you need a container of some sort for a lot of it (spring/ hibernate with JDO would work).
I'm not having a go at their implementation, which seems fine. Its a managed JVM instance, not a container, so they are right in that. However their example does not fit the 'we are replacing java containers', since they use one.
A better example would be to throw away the entire spec, and write a little web server using straight sockets, maybe with a little integration of freemarker or velocity. That would give a web server, with a nice templating language, and could be implemented in 20 lines or so.