Are you using APR (TC-native/JbossNative)?
I will have to say no as my install consist of extracting jboss-4.2.2.GA.zip and configuring the default configuration.
I decided to take a closer look at JBoss Native and here is what I did:
downloaded JBoss Native 2.0.6 source
the build generated jboss-native-2.0.6-src-ssl/output/jboss-native-2.0.6-linux2-x64.tar.gz which I extracted into a _tmp dir.
created a $JBOSS_HOME/bin/native directory as the run.sh looks for it there.
placed all the contents of _tmp/bin/META-INF/lib/linux2/x64/ in $JBOSS_HOME/bin/native/
restarted the jboss service and:
2009-01-15 13:57:47,724 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] JBoss Web Services - Native
2009-01-15 13:57:47,724 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
Now my connections as indicated by http://<server:8080>/web-console/status are in Ready state but the OS shows them as "ESTABLISHED keepalive" and the site is serving fine.
Before installing native the "netstat -o|grep 8009" at the application server always showed the connection as "ESTABLISHED off" and not "ESTABLISHED keepalive".
I guess I should have installed native from the beginning. I will keep a close eye on it.
FYI The issues you ran into were likely the result of this https://jira.jboss.org/jira/browse/JBPAPP-366 . The issue has been fixed but the fix is not in JBoss 4.2.3 (and presumably not 4.2.2). We ran into the exact same problem and went with JBoss Native as well.