Unity has some limitations because it doesn't use the latest Mono's generational GC (because it doesn't use the latest Mono at all).
They recommend that you call System.GC.Collect()
whenever you need some memory cleaned up or expect that something did create a lot of garbage. More on it here: http://docs.unity3d.com/Manual/Understa ... ement.html
Otherwise, there has already been a lot of fixes to remove excess memory allocations.
Nobody has reported any more suspicious wastefully garbage-generating code in Spine-Unity, but if you can help us profile or look for some trouble spots, we could maybe find and fix what can be fixed.
Thanks for the reproduction steps.
I don't have a profiler myself so maybe the other Spine-Unity users can tell where and if things can be improved.