English is not my native language; please excuse typing errors.

The current problem has been solved.

The leak has been resolved with a profiler flame map.

The cause of the leak was a JSON utility class that kept loading the class safely when doing toString.