If anyone indeed *does* think that servlets/jsps have unique forms of memory leaks, that are not related to 'common programming errors', but are endemic to servlet programming, I wouldn't mind hearing about them as well.
Prime candidates: Database related resources improperly released. Threads started but not terminated (this got me one time). Bulky stuff attached to long lived sessions. --------- I suggest you write a monitoring servlet for access by developers. Have this servlet capable of dumping the contents of the working ThreadGroup, available memory, max memory, anything else that indicates activity. Bill