Multiple concurrent connections

Grizzly must be dealing better with those, and it is. The test script for this particular run was generating a 200 kB page in several chunks, pausing a little in between to reach total of 30 seconds. Up to 200 concurrent open connections were observed on the server, with Grizzly loading the CPU to 13-14% vs Tomcat taking 15-16%. Difference is not that great, but I hope to exaggerate it by increasing and adjusting the load.

On another note, I start to like console of Glassfish more and more, as I get accustomed to its terms (i.e. what which pool means). Capability to monitor running processes is very convenient.