WSGIPythonPath not updating with new WSGI parameters

I have a couple WSGI application I created prior to the addition of the settings below.

WSGIProcessGroup [app-name]
WSGIRestrictEmbedded On
WSGILazyInitialization On

I just created a new WSGI application in the same manner as the others. When I tried to run it though I kept getting a 500 error, which was coming from a Python ImportError exception. It was unable to find my application's modules. I added the path to the WSGIPythonPath like I did with my other applications, but when I checked sys.path the new WSGIPythonPath wasn't there. I restarted the Apache process a couple times but it still wouldn't update. Finally, I removed the three newest settings, restarted Apache, and my sys.path immediately reflected the changes I had made before. I added the new settings back after verifying that my application works and it broke again with the same error. As a final test I put my application's path in the python-path argument of the WSGIDaemonProcess directive WITH the new settings and it all works.

I looked up these new settings and I didn't see anything saying they cause WSGIPythonPath to be ignored, but that appears to be the case from my experiences. Although, I didn't test this extensively so I'm probably missing some detail. Does anyone know what causes this? Why does WSGIPythonPath seem to get ignored when those three settings are present? Or if this isn't really the case could someone hypothesize as to what happened?

It's not a huge inconvenience, but it was a bit of a head-scratcher for a bit, because I thought I was forgetting a step from my previous applications.

Thanks!