webwork Query cache is unbounded - and its putting in unbounded string

The webwork Query class has a cache of previously parsed (but not executed) EL strings.

Anything that is thrown at Webwork is cached forever statically. A memory dump reveals strings like

"com.atlassian.jira.web.action.ViewIssue@2345", "com.atlassian.jira.web.action.ViewIssue@63434", "com.atlassian.jira.web.action.ViewIssue@7373434"

These will never be re-used and the dump I saw had 145MB of these guys for JAC.

I think this cache can be killed. Its the "parse" of the EL string into Object "segment" representation.

My gut feel is that computationally it small yet memory wise it has a large and growing impact.

We should kill the cache or limit its size somehow.

SimpleText in webwork does the same thig but not as bad.