Hi Matej Novotny, hi Antoine Sabot-Durand,

Thanks a lot for your detailed responses! If the current Weld 2.3.5. behaviour is the expected one, I think you can go ahead and close this ticket as "won't fix". I already suspected that the behaviour difference between iterator().next() and get() in Weld 1.1 is rather a bug than a feature and your comments confirmed this assumption. This means our current workaround to avoid the memory leak will stop working in newer versions and we need to explicitly destroy the newly created instanced before we migrate the application to a newer Weld version.

Thanks
Andreas