We are using JBoss Portal 2.7.2 and seeing a gradual memory build up when a user is logged into the portal

The old gen becomes full and then we see CPU usage at 100% - doing GC
Took a heap dump and analyzed using "jhat"

Topping the list of instance count we see:

org.jboss.portal.common.text.FastURLDecoder$LookupTerm

Even when we have a look at the heap histogram we see

class [Lorg.jboss.portal.common.text.FastURLDecoder$LookupNode

taking a lot of heap space; this seems to be holding a reference to

LookupTerm

Is there a known leak? Also any inputs on when this is used also might be of help

Thanks
Venu