Large allocations in EJBContextImpl#isCallerInRole

In our application we have the need to know the roles of the current user. We would like to do this using Java / Jakarta EE APIs rather than rely on WildFly implementation classes. We do this by iterating over all roles, which we know statically, and calling EJBContext#isCallerInRole for each one. This seem to be a common technique, see How to get user roles in a JSP / Servlet.
That's about 100 roles for us. We were expecting that would be a lookup into a HashMap or similar with O(1) complexity and almost no allocations.
This however does not seem to be case as EJBContextImpl#isCallerInRole seems to do the role mapping for every call. This results in a large amount of allocations. In our case this completely dominates our allocation profile. See attached screenshot from JFR.