Re: AfxOleInit() and CoInitializeEx in a non-GUI thread ?

Looking at the code that sets up our DCOM server interface, I have the
following.
1.) The MFC Application Starts. InitInstance is called, etc.
2.) Many worker threads are started.
3.) A dedicated thread is started for the DCOM interface

Our separate DCOM worker thread does the following:
--
AfxOleInit();
AfxEnableControlContainer();
CoInitializeEx(NULL, COINIT_APARTMENTTHREADED);
...
while(...) {
   // Wait for COM calls or for app terminate
   MsgWaitForMultipleObjectsEx
   ...
   // Dispatch COM calls in this msg loop
   while (PeekMessage(&msg, NULL,0,0, PM_REMOVE)) {
     DispatchMessage(&msg);
   }
   ...
   // Here comes some code to callback registered clients via our
   // dispinterface ...}

...
CoUninitialize();
--

Now I know that AfxOleInit() will already call CoInitialize().

What I do not quite get is what point this call and the call to
AfxEnableControlContainer() could possibly serve in a worker thread.

A very quick test shows that removing them doesn't seem to affect any
operations.

Can anyone tell me what complications we could expect down the round if
we were to remove the call to AfxOleInit and AfxEnableControlContainer ??