This is a known 'closed as by design' bug / feature of SQL Server 2012.
See connect item Failover or Restart Results in Reseed of Identity
The feature was implemented by Microsoft to fix a regression issue caused by how they handle the new sequence data type. The identity range jump occurs after a instance restart, for all tables defined with an identity value, that have had one or more rows INSERTED since the last time the instance was started i.e any active table.
SQL Server will pre-allocate and jump the IDENTITY range by 1,000 values when the column assigned the IDENTITY value is created as an INT and 10,000 values when defined as a BIGINT.
There are currently 5 workarounds described in the bug report, how ever none of them are terribly palatable. Does it really matter that there are gaps in the sequence, what would happen to your application if a row defined with a IDENTITY value is deleted, or inserted and then rolled back? In both cases a gap in the IDENTITY range would be introduced.