Fixed what seems to be a bug in the JSCEmitter constructor.
Added the finalize callback (JSObjectFinalizeCallback) for the struct creation case. Without this, there is a memory leak for structs created on the stack in C.

// MyPoint.h/.i
struct MyPoint
{
	double x;
	double y;
};
struct MyPoint MyPointMake(double the_x, double the_y);
struct MyPoint AddPoints(struct MyStruct struct1, struct MyStruct struct2);

// MyPoint.c
struct MyPoint MyPointMake(double the_x, double the_y)
{
	struct MyPoint ret_struct = { the_x, the_y };
	return ret_struct;
}

struct MyPoint AddPoints(struct MyPoint struct1, struct MyPoint struct2)
{
	struct MyPoint ret_struct;
	ret_struct.x = struct1.x + struct2.x;
	ret_struct.y = struct1.y + struct2.y;
	return ret_struct;
}

// Javascript
	var struct1 = example.MyPointMake(1, 2);
	var struct2 = example.MyPointMake(0, 0);
	struct2.x = 10;
	struct2.y = 200;
	struct2.z = 3000;
	var ret_struct = example.AddPoints(struct1, struct2);
	var ret_x = ret_struct.x;
	var ret_y = ret_struct.y;
	var ret_z = ret_struct.z;

All this works, but it is leaking the structs created by MyPointMake() and AddPoints() without the finalizer.
When function pointers are bound, the generator creates code that calls SWIG_ConvertFunctionPtr and SWIG_NewFunctionPtrObj. These are not implemented in the SWIG/JSCore implementation yet. Without these, compiling will create linker errors.

Since I'm trying to test stuff, the linker error prevents me from testing other functionality I care about. So I'm taking a cue from some of the other generators like Perl and just defining it to the regular Ptr versions. I don't know if this is the correct thing or not. Oliver's SWIG JSCore/v8 document says they don't know what to do about function pointers yet.