Please upgrade to Ruby LSAPI 1.7 if you have not done so.
What you observed is normal for current release because the way rails process being started. There is one ruby process which only fork/manage children ruby worker process to handle requests. The process manager in the parent process is allowed to start 2x processes configured under certain situation.
So, when "Max connections" set to 1, you may see 2 ruby processes normally, and 3 in the worst case.
We probably should skip the process manager in the parent process when "Max connections" has been set to 1, as it uses almost twice the resources.