Originally posted by bittoo garg: Is there any pitfall of this? How developer's work effected by this functionality of the servlet engine?
It's best not to be storing user specific state in a servlet in the first place as multiple users will access it. There could be state that applies to everyone - such as a data access object reference. In this case, you would want the data to be be serializable if your server implements hibernation.
I don't see the value of duplicating the servlet. The server could just create a new one.