This is a bug in the data provider, which has been logged in the Firebird issue tracker. The reporter of that bug has kindly provided a fix.
The fix has not yet been incorporated into the official release, but I was able to download the provider source and apply the fix to get past this issue with my application.