it appears they are working on a 3.3.1 release -- which hopefully will resolve the resource leak.
I'd say it's a little too early to call this one definitive, however I should know by tuesday morning (monday is a holiday for us) if this issue is still present with these jars in place. 