I'm just responding for my own situation...
Of course tying my memory bloats to RDP is pure speculation, and my post was not trying to generalize the problem beyond my circumstance. Given that the problem is so very difficult to diagnose, and the tools insufficient, what else do you expect users to do?
So we're left with creating and testing theories, and trying to find some cause and effect. Your advice is to remove things, and see if the problem does not reoccur. It is good advice. I'm pretty confident I found the trigger in my situation, and that's good enough for me, since at the end of the day its about avoiding the problem.
I mentioned in my old post - you and I use RDP with different clients, yours stable, mine crashing, aborting, failing to quit, and failing to reconnect w/Windows multiple times per day. Mine is considered "unsupported" for any Mac OS X version in the past couple of years (Microsoft has essentially abandon the tool - they haven't touched it since 5/5/2011).
I agree that the guide and tools are useful. But I hope also that you can agree, they are also severely limited, and in some situations, where the recurrence takes a long time, not possible to use as they do not support long-term use - they crash.
I think we'll all agree, it can be a very difficult problem to resolve.