"Dirty" would be a good description
. Two of the three seem to mainly force working set trimming (which can cause huge performance hits, not to mention the potential for bugchecking if the app being "cleaned" is doing even the slightest thing wrong with it's allocations), and the other appears to simply do what the memory manager would already do, it just calls the APIs agressively (which is the safest way, I suppose, but isn't likely to actually do much if an app is leaking other than fill up your paging file, which can cause bugchecks in and of itself if applications are indeed leaking memory - you just delay the inevitable).
So, dirty, yes. Advisable, no