Azure Table Storage Exception: 409 Conflict unexpected?

A nice workaround could be:

if (!container.Exists())
        {
            container.CreateIfNotExists();
        }

CreateIfNotExists is throwing the exception.
There was a change in implementation of the method CloudBlobContainer.CreateIfNotExists or CloudTable.CreateIfNotExists.

The implementation in the 7.1.2 storage client library is the following:

1. Make a call to check to see if the storage container or table exists (HTTP HEAD request).

2. If it exists do nothing.

3. If it doesn’t exist then make a call to create the container or table.
    

In the storage client library 8.1.1 the implementation is the following:
 

1. Make a call to create the container or table (HTTP PUT Request).

2. If an error was returned (HTTP 409) because the container or table already exists then do nothing. The error is handled.

3. If the container or table did not exist then create would have succeeded.

I checked with 9.0 and that behavior still exists