To bring some real-world numbers in to this, a Western Digital VelociRaptor (10K RPM) draws 6.2W while reading or writing, and 4.3W while idle but online. An Intel X25-E 64GB draws 2.6W while reading and writing, and 0.06W while idle. Let's assume that you have 7 of the SSDs in a non-RAID aggregated volume, and one of the 450GB VelociRaptors, and you're streaming data to and from them at the fastest rate the VelociRaptor can handle. In order for the SSD array to draw as much power as the active VelociRaptor, you have to average 2.3 SSDs active at once. If the transfers are mostly sequential, you will basically never have more than two SSDs active at once. If you have random accesses, then you can obviously get many of the SSDs active at once, but they can all fulfill their requests and return to idle before the VelociRaptor has served the first request. In order for your SSD array to average the same power consumption as the VelociRaptor, it would have to be executing about 7.7K random 4KB writes per second, or 83K random 4KB reads per second. That difference in performance is big enough that the power draw of SSDs will never be a net disadvantage, and the running cost of an SSD-based solution will not be higher than the running cost of a hard-drive based solution.
[1]I was talking in the grandparent post about optimising for online gigabytes per watt. I'm assuming we still are, because SSDs are a huge win except for this instance. If we're talking about performance, SSDs are so much better than mechanical there's basically no comparison. Optimising for online gigabytes per watt, your servers will have the maximum number of hard drives installed, always.