CHEF-3104 added support for running chef (client, solo) runs in a forked subprocess. This fixes all but the most egregious memory leaks caused by either chef bug or recipe bug. This is a huge win since users have a wide variation in programming skill level and may not even recognize it if they're creating a memory leak.
As Windows does not support forking, this option does nothing on Windows. Chef should have a functionally equivalent mode of operation that works with Windows' process model. This could be a separate command line program that is more low-level than chef-client/solo, or perhaps a change to the windows service code.