Testing locally here, the leak does NOT appear to reproduce using the .NET
Framework on Windows (via Visual Studio 2013).