Memory leak in Jelly Runner while using AddComment tags

While running a large import Jelly script (85,000 comments added), we noted what appears to be a significant memory leak. It is problematic because this makes it a bit of a crap shoot as to whether the job will finish and because each addcomment is atomic, the incomplete jobs leave us with a messy state to sort out (e.g. figure out which comments were added multiple times because the job was rerun).

Symptoms include odd behavior of the job and very high, non-decreasing memory utilization post batch. The job runs very rapidly for a while and then mysteriously pauses for -2-3 hours before continuing at a much lower throughput. Sometimes, the job hangs with apparently, no hope of ever finishing. When the job is complete, memory utilization remains extremely high (e.g. > 95%) and never comes down...even when garbage collection is forced. The only resolution is to bounce the server.

Other notes:
1. The entire job consisted of AddComment Jelly tags
2. The source file was locally stored on the server (so no funny business with network latency or something along those lines)
3. The server was bounced prior to the start of the job to insure that there was no DB lock or system resource contention
4. There was no non-Jira related activity on the system during this process (e.g. backups)
5. E-mail notifications were disabled during the running of this script

Thanks,
Ted