dlopen called twice on plugins

It appears lcb_destroy() is not calling lcb_destroy_io_ops() (or however it's handled for default conditions) as I am getting valgrind memory "leaks" (ok, it's not really a leak but it's not a clean shutdown) in my example modules - This can be recreated with minimal.c from the shipped examples.

No, not using a custom io_ops structure :>

==6625== 32 bytes in 1 blocks are still reachable in loss record 1 of 2
==6625== at 0x4C267BB: calloc (vg_replace_malloc.c:593)
==6625== by 0x567030F: _dlerror_run (in /lib64/libdl-2.12.so)
==6625== by 0x566FEE0: dlopen@@GLIBC_2.2.5 (in /lib64/libdl-2.12.so)
==6625== by 0x4E73E32: ??? (in /usr/lib64/libcouchbase.so.2.0.33)
==6625== by 0x4E741F5: ??? (in /usr/lib64/libcouchbase.so.2.0.33)
==6625== by 0x4E74499: lcb_create_io_ops (in /usr/lib64/libcouchbase.so.2.0.33)
==6625== by 0x4E6EEAE: lcb_create (in /usr/lib64/libcouchbase.so.2.0.33)
==6625== by 0x401840: main (in /home/mleib/CSrc/a.out)

==6625== 56 bytes in 1 blocks are still reachable in loss record 2 of 2
==6625== at 0x4C27A2E: malloc (vg_replace_malloc.c:270)
==6625== by 0x400E394: _dl_signal_error (in /lib64/ld-2.12.so)
==6625== by 0x401270F: _dl_open (in /lib64/ld-2.12.so)
==6625== by 0x566FF65: dlopen_doit (in /lib64/libdl-2.12.so)
==6625== by 0x400E285: _dl_catch_error (in /lib64/ld-2.12.so)
==6625== by 0x567029B: _dlerror_run (in /lib64/libdl-2.12.so)
==6625== by 0x566FEE0: dlopen@@GLIBC_2.2.5 (in /lib64/libdl-2.12.so)
==6625== by 0x4E73E32: ??? (in /usr/lib64/libcouchbase.so.2.0.33)
==6625== by 0x4E741F5: ??? (in /usr/lib64/libcouchbase.so.2.0.33)
==6625== by 0x4E74499: lcb_create_io_ops (in /usr/lib64/libcouchbase.so.2.0.33)
==6625== by 0x4E6EEAE: lcb_create (in /usr/lib64/libcouchbase.so.2.0.33)
==6625== by 0x401840: main (in /home/mleib/CSrc/a.out)