tss::set(0) leads to double-free

[perfecthash]

This bug only occurs on non-pthreads platforms such as
Win32 where no automatic destructor is available.  I
declared a variable:

boost::thread_specific_ptr<X> pX;

and initialized it:

pX.reset(new X);

Later, I did

pX.reset();

Subsequently, when pX went out of scope, it tried to
delete the X instance again.  It's easy to see why. 
tss::set checks

if (value && m_cleanup) {
   update cleanup handler table
}

So if value is NULL, the original cleanup handler is
left lying around.

[perfecthash]

Logged In: YES 
user_id=173374

Looks like this got fixed in Boost 1.32, thanks!