@christian: without looking at the code: could it be we’re seeing a CDI lifecycle issue here? like that the configuration bean is created multiple times and we parse the configuration in the constructor instead of a @PostConstruct method? That would explain why the configuration is parsed more than once per request.
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.