First of all, in case you're thinking of automatically doing an "Update Service Reference" in your CI build for every service reference, think again. You don't want to do that - you want to think about it ahead of time, do the updates for each referencing project, build them locally, run their tests, etc. You don't want the build doing that for you just because there's been a change in the contract - the clients might not yet be read for such a change.
Second, I think the only useful definition of "breaking change" in this context is to run all your automated tests, and see if any break. That's what CI tests are for in the context of other code; why make it different for services?