I ran into a similar problem (my ISP graciously allows php on my personal homepage.) I assume the reason you need to chown is to give write access to php.
In my case, the webserver is running as user "www-data", group "www-data"...but all of my personal page stuff is under my username.
The workaround was to write a quick php script to create a file (or whole directory), then to ftp into my public_html directory, create a directory for www-data to be able to write in, momentarily chmod it to 777, access the script from my browser to create the directory (which was then created with the owner 'www-data' so the webserver can do things in it), then to chmod the directory back to normal.
The result is a webserver-writable folder that I can keep php-generated logfiles, temp files, data, etc. in without making it world-writable.
Hopefully this helps...