The vision for ArcGIS Server is to publish pooled map services for consumption by web users. The map services can be extended via an SOE which can also augment the ESRI SOAP and REST endpoints.
It is important to understand what ESRI is doing in 10.1 because it provides insights. In 10.1 the ability to publish non-pooled services is eliminated. In addition the set of APIs, i.e. interfaces which can be accessed by the SOE is greatly restricted. My hypothesis is as follows:
1) ESRI does not want you making changes to the map service that might affect other users
2) ESRI is moving server to 64 bit only and they want to minimize the set of ArcObjects that they have to make work in this context
The reason I mention the above is that the ability of ArcGIS Server to be a platform for providing general web services is being diminished.
What I think that is that if you want general web services then you have to use ArcEngine and do it yourself. For example, we want to provide a web service which is able to create a new SDE version, place features in it, and then reconcile. How would we do that using ArcGIS Server in 10.1?
I mention 10.1 because we want to write software which will work in the next release.