I encountered a strange problem with enumerable_thread_specific: a enumerable_thread_specific object got deleted prematurely when a root task using it was spawned from a variadic template function (which I added for convenience to a base of the task). See attached code. Tested using gcc 4.7.0 and 4.8 only.
It seems that, for some reason, the scope of the enumerable_thread_specific object is truncated when the variadic template is used for spawning the root task. In case the thread local object's destructor de-allocates from the heap, I get a segmentation fault (not with the simple test code attached).