Because I'm keeping an external resource open, a socket, that is created and removed with the bean.
Also, I thought that was the whole point of stateless session beans - performance.
I don't believe this is normal behaviour and I'm pretty sure 3.5.1 doesn't do it ?
And I can't believe no one else has experienced this ?
Come on you guys, who would prefer their stateless session beans to be instance pooled correctly, I know I do !!!