Maybe the respective apache child could connect to the persistent ssh via sockets (e.g. unix domain sockets)?

I.e., the user's session would hold a number which corresponds to the ssh/socket that was initially started for the user. The socket would then simply serve to forward the stdin/stdout pipes of the ssh being run in a separate process...