In what browser does that reproduce?
We are not 100% sure of that memory leaks. So I've asked here in case it is a known issue.
I explain the test made, in case you encounter it a valuable one.
I launch that famous example of the table cars (rich:scrollableDataTable & DataTableScrollerBean).
In Internet Explorer 6, first load page consumes 28.788 kb of memory. And after 100 page reloads the memory consumed reach to 29.428 kb. I don't know if that difference of 640 kb allows us to think about a memory leak attributable to scrollableDataTable.
Any appreciation will be welcome...
Memory leaks show much bigger increase in memory consumption (megabytes and tenth of megabytes), 640kb per 100 requests doesn't look like noticeable leak at all.
(Thanks for your reply, Nick!)