physics: deallocate thread_config upon exit(revert)

Yep, looks like the threads themselves are lazily booted up and may or may not reach the barrier before the main program does. I am cooking something up to replace the stone-age counter we have along with statistics. That should make the whole thread_conf obsolute.