(Edit: a few others in this thread are observing that most PHP-ers got their start in the early 2000's. To add another datapoint, that's true in my case as well. Active since 1998, I started with perl, got familiar with PHP, moved on to MS tech for a few years, then became a RoR dev in ~2005-07. Eventually I got frustrated with Rails' performance, decided to refactor an app in PHP and was blown away by the two-orders-of-magnitude performance difference at the time. I've stuck with PHP since then, though I still play with Node and Python. All great tools. I hate the language wars, use whatever works for you.)
As another example, I'm still astonishingly productive with PHP for backend APIs and rapid development projects. The symfony/Doctrine community has done a phenomenal job at bringing world-class tools to the language.
It doesn't really matter what you use if it gets the job done.
I don't see how the young people of today decide to go with Ruby, with it's terrible performance, and especially last year with it's slew of vulnerabilities. If you like the beauty of Ruby, use it on your own stuff or for learning. But using it with intention for a production environment? I just don't get it...
Rails was embraced because it provided a clear way to write DB-driven web apps with minimal configuration, following a strict pattern. And a lot of people sort of like strict.
So to complete the guess I think if you focus on the teams with older technical founders you might find some PHP but in the teams with younger technical founders I doubt that that would have a high incidence.
Joel Spolsky had some interesting things to say here: http://www.joelonsoftware.com/items/2006/09/01.html