With connection pooling being deprecated since mongo 1.2.3 you can no longer get or set the size of the pool (the connections stored in there to be fetched when there is a demand). Connections are managed by PHP and that means that it stores 'hashes' containing information such as host, port, database name, process id etc that identify a unique connection.
You can set the maximum simultaneous connections though (persistent is the new default as you mentioned) through the actual mongod process if you have access to, not through PHP. Server-side, you can run a mongod instance with the parameter --maxConns = 5000 to control the maximum connections for it.
Persistent connection lifetime is not adjustable or viewable as of yet. You would not really need it anyway as new connections overwrite old ones. Unused persistent connections do no harm and new ones get registered, pushing old ones out. The lifetime therefore depends on the amount of new connections at each time.