Using a named scope mock results in memory leak unless global scope is used for clear()

[icvidal]

I can't find if this behavior is documented/designed: when using a mock with a custom scope, it requires using mock().clear() instead of mock("<SCOPE NAME>").clear()

The following example illustrates the issue:

#include <CppUTest/TestHarness.h>
#include <CppUTestExt/MockSupport.h>

TEST_GROUP(NamedMockFailure) {
};


TEST(NamedMockFailure, TriggerFailure) {
    mock("NamedMockFailure").enable();
    mock("NamedMockFailure").checkExpectations();
    mock("NamedMockFailure").clear();
}

TEST(NamedMockFailure, SeemsToWork) {
    mock("NamedMockFailure").enable();
    mock("NamedMockFailure").checkExpectations();
    mock("").clear();
}

Can anybody confirm if this behavior is expected? If so, can you point me to it's documentation?
Thanks!