TempDisableService {
   $object->DoSomething();
   $object->DoSomethingElse();
};
[download]

(...) but it could also introduce some confusion.

That's exactly the point...  Although I do like the syntactic elegance (and would consider it a good use of prototypes), I'd say that employing such a rarely seen facility does not necessarily make it easy to comprehend for anyone with only a cursory knowledge of the language (in case the understanding is supposed to go beyond merely being able to apply the recipe "just put braces around what to run"...).  OTOH, if you document it, and make sure people come across the explanation before encountering the fancy construct, I'd say stick with it.

(Side note: as an advocate of self-explanatory function/method names, I'd prefer something like "run_with_service_disabled" (or "runWithServiceDisabled" if you like), because that'd make it more obvious that what you pass in is something to run, and not some parameters controlling how to temporarily disable a service. </nitpick :> )