free c-strings after conversion to go strings

although im not 100% sure, i dont think go will free them at will as they
are not allocated by go itself, which would make it quite unsafe to do so.
if so, before this fix, the strings would be leaked and never freed...
Merge pull request #3 from mercora/memmory-issues

free c-strings after conversion to go strings