Investigate performance impact of disabling jsp pooling by Tomcat container

the c:forEach tag holds references to objects as long as release() is not called. It is up to the container to call release().

For the HST, this results in possibly an entire old hst model can be kept by jps's as long as they are not called again. Even worse, every jsp can keep a reference to some old hst model, so there can be up to several hst model objects which cannot be garbage collected.

We either provide a hst:forEach tag that takes care of it , that can be used instead of the c:forEach tag, or, we check the performance impact of disabling jsp pooling by the container.

Also see

https://issues.apache.org/bugzilla/show_bug.cgi?id=25623
https://issues.apache.org/bugzilla/show_bug.cgi?id=33934

The issues won't be fixed