honestly, I don't get it. This should not happen.

Ah, now I get it. Sorry, I'm coding a damn LOT of squirrel, but I seem to intuitively do this right (initializing in code, never in definition)

The exact explanation would be:
though each class instance clones the class definition and has its own member "times", those members are simply a reference to the ONE AND ONLY table inside the class definition.
Or, in other words... In any assignment ( a=b;) the object is RIGHT hand(b) and left hand (a) is always a reference. (unless right hand is a literal/intrinsic value)
And squirrel never clones deep!

same as...
local a={ test="123 } ; //resembles class definition

local b=a ; //assigns b a reference to a!
print (b.test) ;
a.test="pwnd!"; //so that a change of a.test...
print (b.test) ; //...reflects in b!


Another similar pitfall:

function dosomething_with(sometable)
{
local b=sometable ;
b.changed<-true ; //adds that also to sometable ;
b=clone sometable ;
delete sometable.changed ;
//now table doesn't have the slot "changed" anymore, but b still has because it was explicitly cloned
return b ;
}

//note, however:
local demonstration=["Be aware!"] ;
local st={ somedata=1234, someotherdata=demonstration } ;
local test=dosomething_with(st) ;
print(st.someotherdata[0]) ; //will print "Be aware!" as expected
print(test.someotherdata[0]) ; //and this will, too!
demonstration[0]+=" Bugs!";
print(st.someotherdata[0]) ; //will print "Be aware! Bugs!"
print(st.someotherdata[0]) ; //will print "Be aware! Bugs!"