Yes, you are correct. Nested graphs are only initialized when they are first encountered (lazy initialization) and this is why at the first encounter only and due that initialization/deserialization, there is naturally garbage generated.
I am already looking at adding an option to “pre-initialize” everything if required, but it’s not something that is possible right now.
If you are in a hurry though, I can tell you some quick source code changes to make this happen.