Since a CLR thread is identical to a Windows thread and assuming that the current thread is a worker thread managed by the thread pool, what may happens if the thread is destroyed and re-created later by the pool using the same unique identifier?

I personally find this scenario extreme (in the context of a TDD tool) so I am just writing it here to reflect my thoughts on storing a thread's unique identifier instead of the thread's instance itself.