Unable to create role via REST when role name is a portion of an existing role name

When creating roles via REST, if the name of the role that is being created is a portion of an existing role name then the new role isn't created.

For example, if we have a single role that exists with the name "TESTER", and we try to create a new role with the name "TEST", instead of the new role being created we receive a 400 - "can not create new role: TEST. it already exists" response.