This is by design in SQL server. SQL Server guarantees that the next number generated will be unique and incremental, it does not guarantee it will be in sequence.
This started in SQL 2012. Simply restart the service to repro the issue. It is well know change in behavior, it has always been documented this way, and is marked by design. Its just an unexpected change in behavior
