The difference here is that Apple isn't writing high level Objective-C code for the core operating system. So it is not as easy as checking a box, they would have plenty of assembly code to port over from x86 to PPC especially with the performance enhancements they are doing with OpenCL. By eliminating PPC support they save many man-hours porting machine code back to PPC.
Okay, it's not always that easy as checking a box in Xcode. There are some nuances like little endian, big endian, %d, etc.
But claiming that eliminating PPC support will save man-hours in porting is just not right. I work for a company which ports x86 Windows apps into Universal apps for OS X. Some of those apps are huge with millions of lines of code. I can say for sure that porting/building Universal apps is not at the cost of man-hours!
The main reason OS X ports will become Intel only is performance. Future programs will need more power/performance. The only way for getting more power/performance is new/future hardware. Apple has chosen for Intel hardware so it's therefore logical that the solution will be Intel only programs. Not because building/porting a Universal program (or even a system) costs more in man-hours.
About OpenCL: OpenCL is a technology that will run mainly on future hardware. At this time only a few Intel Macs are capable to make "full use" of the "current" technology/specs.
OpenCL is "OPEN" (not CLOSED). Open is not only Intel or nVidia. Open will be Intel, PPC, ATI, nVidia & many more.
A quad core G5 (even a dual proc) with a high end GPU is in a way equally OpenCL ready then a current Intel Mac. It depends on the hardware and how many of the "current" optimized OpenCL code will be utilized.
Sure the latest/newest hardware/mac will have the highest benchmarks with OpenCL fully utilized. But that does not mean that the quad G5 will not benifit from OpenCL (optimized for PPC G5).