Take a look here maybe it helps. It is a bug in org.apache.jasper.runtime.BodyContentImpl and has memory leak.
A possible solution:
"As Jeff notes, the option -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true is available in 5.5.15 onwards"