UP-4143 EventSession purge fails to page, OutOfMemory can result

From ticket ...
As a uPortal adopter, I would like my portal to not run out of memory when it tries to purge a large number of EventSessions.  JpaEventSessionDao in purgeEventSessionsBefore() attempts to load all the matching sessions and then step through the list deleting them one by one, rather than loading them in smaller batches. This can result in an out of memory.

See uportal-dev@ thread re: http://thread.gmane.org/gmane.comp.java.jasig.uportal.devel/5743 .
OK.  One more quick question.  Could we split the transaction out so that only 100K events are deleted in a transaction instead of holding it so multiple batches of 100K events are deleted in the transaction?  I think we have AspectJ AOP enabled so you can have a transaction in another class method and the annotation would be properly processed.  Thoughts?