### Description of problem:

JBoss does not check "Connection: close" in response header. It should be checked and JBoss is better to disable keep-alive and close connection when  "Connection: close" exists in response header.


### Steps to Reproduce:

Access JSP or Servlet application, which set "Connection: close" in response header, running on JBoss. For example, calling response.setHeader("Connection","close"); in JSP.


### Actual results:

JBoss does not send FIN packet and the connection is still opened (keep-alived) after response is completed. 


### Expected results:

JBoss sends FIN packet and the connection is closed from JBoss after response is completed.


### Additional info:

Apache httpd and Jetty send FIN packet and the connection is closed from the servers when "Connection: close" header is specified in response. In addition, as far as I heard from the customer, Weblogic also does.

HTTP/1.1 RFC2616 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.10) states the following:

~~~
14.10 Connection

HTTP/1.1 defines the "close" connection option for the sender to signal that the connection will be closed after completion of the response. 
~~~