I am creating numerous worker threads using _beginthreadex and terminating them with _endthreadex(0) and CloseHandle().

When taking a memory snapshot in Visual Studio, a memory leak of 480 bytes per thread occurs at 

MyApp.exe!_AFX_THREAD_STATE.

The call stack is as follows, confirming that the memory was allocated by the Toolkit during thread creation: 

kernel32.dll!0x7ff96021257d() 

MyApp.exe!CXTPSkinManagerDetoursApiHook::ThreadProcHook() - Line 591 

MyApp.exe!AfxGetModuleState() - Line 314 

MyApp.exe!CThreadLocal<_AFX_THREAD_STATE>CreateObject() - Line 200 

MyApp.exe!CThreadLocalObjectGetData() - Line 453 

MyApp.exe!CThreadLocal<_AFX_THREAD_STATE>::GetData() - Line 179 

MyApp.exe!CThreadLocal<_AFX_THREAD_STATE>::operator _AFX_THREAD_STATE *() - Line 191

It seems that using AfxBeginThread instead of _beginthreadex can avoid this issue

My application creates and deletes a very large number of threads, so I cannot overlook this small memory leak. 

Additionally, the libraries my application depends on also seem to create threads, making it impossible to replace all thread creation with AfxBeginThread.

Is there any workaround for this issue?