Major Description
The current default logger is not thread-safe. That's no problem as long as it's known. One can use his own logger. However, the axutil_env_create_with_error_log() function internally first creates the default logger and then deletes it again to be replaced by the specified logger. Since even creating / deleting the default logger is not thread-safe, this leads to problems (in my case an assertion in the vs runtime dll).
When a logger is specified for axutil_env_create_with_error_log(), the default logger should not even be created.
