Description:
------------
First I want to thank you for this plugin. It's great and this is the first problem I encounter, since I use it. I guess, thats, why there no bugs in the bug report list. :)

When I make a persistent connection to a database file, the database file will be locked for filesystem operations like move or delete, until I restart the webserver.

I think, the problem to this is because php doesn't free the resources of the persistent connection. I am aware that this is the normal behaviour for persistent database connections in php.

The normal solution to this problem is to free the resource on the db-side or with a connection timeout(never tried it) in php. Unfortunatly neither of them work with sqlite since there is no server or connection timeout directive.

I don't know if this is known or even intended behaviour. I'm sorry, for this (miss)post if this is not a bug. 

I tried it with php 5.1(precompiled sapi for apache2) (4 days old) and sqlite included with it ( and of course I uncommented the extension directives to enable pdo and sqlite modules in php.ini). I dont know if this problem does exist in other versions. But I expect, that this issue exist in all but the cgi version of php.

thank you in advance,
Sebastian Lublow
Student at the University of Groningen, Netherlands

P.S. This is my very first bug-report and english is not my native language. I appologize for any inconvenience resulting from that.

Reproduce code:
---------------
$handle = sqlite_popen('persistent.db');
sqlite_close($handle);

Expected result:
----------------
The database file can be deleted/moved after execution of the code (or at least some timer after execution).

Actual result:
--------------
The database file persistent.db cannot be moved/deleted, until the webserver restarts. There appears no default connection-timeout for idle connections. (I waited almost a day for a connection-timeout.)