Even if Java EE containers are more and more commonly used for daemons and standalone applications, most of the developed applications are still web applications and, therefore, use HTTP either as clients of another server or as the server themselves.
In the last sentence, Java EE containers include the wide embedded varieties of containers such as TomEE Embedded, Apache Meecrowave, WildFly Swarm, and so on, and is not limited to standalone containers or full profile servers.
This means that the Java EE configuration will have to deal with HTTP configuration. It needs to be handled at multiple levels (networks, HTTP caching, and so on) but also in multiple layers (server/HTTP connector, client connection pooling, SSL ...
