In normal use jakarta.el.ImportHandler class may be asked to resolve non-existing classes. It tracks failed Class.forName attempts to avoid the cost of more such attempts. But, an ImportHandler's lifecycle is scoped to a request, so this tracking doesn't prevent potentially many calls.
 
One place that may validly make such calls is jakarta.servlet.jsp.el.ScopedAttributeELResolver. We used to maintain a JBoss fork of the Pages API that included cache miss tracking in ScopedAttributeELResolver, but we no longer maintain that fork. So, instead, add it in the JBoss variant of Jakarta EL. The use case is similar to other similar caching, with such caching being the reason we maintain the JBoss variant of EL.
 
Note that for EE 12 it looks like the EL and Pages API projects at Eclipse will handle this particular use case, so this won't become another reason to keep using JBoss version of the EL API.